Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(artifact-registry): Add support for CMEK #1452

Merged
merged 6 commits into from
Jun 20, 2023
Merged

feat(artifact-registry): Add support for CMEK #1452

merged 6 commits into from
Jun 20, 2023

Conversation

alloveras
Copy link
Contributor

Intent

To extend the Google Artifact Registry module to support enabling encryption at rest with a user-supplied KMS key.

Problem

Most of the FAST framework encourages and supports the use of CMEK keys. While using the framework, we've found that we couldn't use this module to provision Google Artifact Registry repositories because the default organizational policies enforce repositories to be encrypted at rest and, the current version of the module, does not support passing in a KMS key to enable encryption at rest.

Solution

To extend the module API to optionally accept a KMS key name to be used to encrypt the artifact blobs' at rest.

@juliocc juliocc enabled auto-merge June 20, 2023 07:06
ludoo and others added 4 commits June 20, 2023 17:27
#1446)

* fixup(project-factory): Use the correct KMS Service Agents attribute name

* Add new KMS bindings to tests

* Update test resource counts

* Update README.md resource count
auto-merge was automatically disabled June 20, 2023 07:27

Head branch was pushed to by a user without write access

@juliocc juliocc merged commit 00e9d20 into GoogleCloudPlatform:master Jun 20, 2023
@alloveras alloveras deleted the alloveras-gar-cmek-support branch June 21, 2023 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants